Rhapsody Developer Release Copyright 1997 by Apple Computer, Inc. All Rights Reserved.

Rhapsody Developer Release Notes:
Developer Documentation

These notes concern developer documentation for Rhapsody and the delivery of this documentation.

Notes Specific to Rhapsody Developer Release

New Features

• Developer documentation is now mostly in HTML or PDF format (on both Rhapsody and Yellow Box for Windows platforms).
  
  
• For the Developer Release, you can access documentation through Project Builder's Help Menu. Chose the Help option to display a "home page" from which you can display or learn about documentation. You can also view documentation using a standard HTML browser. Most documentation files are located in NextLibrary/Documentation/NextDev; Application Kit and Foundation reference HTML files are located in a localized subdirectory of the framework's Resources directory.
  
  
• The Yellow Box framework reference documentation (Application Kit and Foundation) has been updated for Rhapsody. In addition, the developer tutorial Discovering OpenStep and the tools reference documentation has been updated for Rhapsody.
  

Known Problems

• Page 148 of the book Discovering OpenStep: A Developer Tutorial shows a code example that contains an error. If, in following the tutorial, you copy the code from the book and compile it, ToDo will crash if you launch the application by double-clicking its icon in the workspace. The method initWithFile: begins in this way in t:he book:

  - initWithFile:(NSString *)aFile
  {
      NSEnumerator *dayenum;
      NSDate *itemDate;
       [super init];
       if (aFile) {
          activeDays = [NSUnarchiver unarchiveObjectWithFile:aFile];
          if (activeDays) 
              activeDays = [activeDays retain];
          else {
              NSRunAlertPanel(@"To Do", @"Couldn't unarchive file %@", nil, nil, nil, aFile);
              return nil;
          }
      } else {
          activeDays = [[NSMutableDictionary alloc] init];
          [self setCurrentItems:nil];
      }
       if (![NSBundle loadNibNamed:@"ToDoDoc.nib" owner:self] )
            return nil;
  /* etc. ... */

  Corrected, the code example should read as follows:

  - initWithFile:(NSString *)aFile
  {
      NSEnumerator *dayenum;
      NSDate *itemDate;
       [super init];
       if (![NSBundle loadNibNamed:@"ToDoDoc.nib" owner:self] )
            return nil;
       if (aFile) {
          activeDays = [NSUnarchiver unarchiveObjectWithFile:aFile];
          if (activeDays) 
              activeDays = [activeDays retain];
          else {
              NSRunAlertPanel(@"To Do", @"Couldn't unarchive file %@", nil, nil, nil, aFile);
              return nil;
          }
      } else {
          activeDays = [[NSMutableDictionary alloc] init];
          [self setCurrentItems:nil];
      }
  /* etc. ... */

  In other words, the statement that loads the nib file should should come right after the invocation of super.

• Much of the compiler reference cannot be read on Project Builder. A bug causes Project Builder to load no more than several paragraphs when the "GNU CC Comand Options" link is clicked. To read the compiler reference, use a standard HTML brower (such as OmniWeb on Rhapsody) and open the HTML files located in NextLibrary/Documentation/NextDev/Reference/DevTools/Compiler (the entry-point file is Compiler.TOC.html).You can also read the PDF version of the compiler reference (Objective-C Compiler.PDF), located in the same directory.
  
  
• Because of bugs in the way HTML is handled, many of the files of the developer tools reference (debugger, assembler, and preprocessor) either are not properly displayed in Project Builder, or take a long time to load completely. If you run across these problems, use a standard HTML browser to read the files in NextLibrary/Documentation/NextDev/Reference/DevTools. Alternatively, you can use a PDF viewer to read the PDF versions of the reference documentation, which are in each tool-specific subdirectory of DevTools.